-- card: 41021 from stack: in
-- bmap block id: 0
-- flags: 0000
-- background id: 3633
-- name: The Critical Path


-- part 44 (field)
-- low flags: 01
-- high flags: 0002
-- rect: left=409 top=260 right=275 bottom=464
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 3
-- text size: 10
-- style flags: 0
-- line height: 13
-- part name: pagexofy


-- part 46 (button)
-- low flags: 00
-- high flags: A003
-- rect: left=15 top=173 right=194 bottom=211
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 3
-- text size: 10
-- style flags: 0
-- line height: 13
-- part name: Setting the Critical Path Threshold
----- HyperTalk script -----
on mouseUp
  go card id 61529
end mouseUp


-- part contents for background part 6
----- text -----
In the standard definition, the critical path is the sequence of tasks that will take the longest amount of time to complete; in other words, it has the least amount of slack time. You can redefine “critical” in MacProject II to mean having slack time equal to or less than a threshold you set. A task on a critical path is called a critical task.



-- part contents for background part 7
----- text -----
If you set dates for tasks other than the first task, your project may have some critical tasks but no critical path throughout the schedule.

If a critical task is not completed by its Early Finish date, any tasks dependent on it will be delayed in starting. Thus, unless the lost time can be made up by completing a subsequent task sooner than planned, the project’s completion will be delayed by the amount of time that the critical task went beyond its allotted time.



-- part contents for background part 27
----- text -----
Schedule Information

-- part contents for background part 28
----- text -----
The Critical Path

-- part contents for card part 44
----- text -----
1 of 2